Payment information technologies

ABSTRACT

A method includes maintaining first payment card information for a cardholder. The method includes processing a first card not present transaction between the cardholder and a merchant. The first transaction based at least in part on the first information. The method includes generating second payment card information for the cardholder. The second information replacing the first information for subsequent use via the cardholder. The method includes receiving an input from the cardholder. The input indicating the merchant. The input based at least in part on the second information replacing the first information. The method includes sending the second information to the merchant based at least in part on the input. The method includes processing a second card not present transaction between the cardholder and the merchant. The second transaction based at least in part on the second information after the sending.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication Ser. No. 61/757,224, filed on Jan. 27, 2013, which is hereinfully incorporated by reference for all purposes.

BACKGROUND

In the present disclosure, where a document, an act and/or an item ofknowledge is referred to and/or discussed, then such reference and/ordiscussion is not an admission that the document, the act and/or theitem of knowledge and/or any combination thereof was at the prioritydate, publicly available, known to the public, part of common generalknowledge and/or otherwise constitutes prior art under the applicablestatutory provisions; and/or is known to be relevant to an attempt tosolve any problem with which the present disclosure may be concernedwith. Further, nothing is disclaimed.

Many people purchase goods and/or services online from merchants, suchas Amazon®, Target®, and others. Such purchases are typically made,whether via the merchants' websites and/or mobile apps, using paymentcard information, such as credit card information and/or debit cardinformation. In order to make such shopping experience simpler, many ofsuch merchants optionally allow for the payment card information to besaved on the merchants' computer systems for future use. Therefore,based on the customers' sign in into the merchants' systems, such as viaprovision of an email address and/or a password, the payment cardinformation is readily available for authorizing payment. However,despite such functionality, there are many drawbacks.

A person's payment card information is often stolen, misused, lost,expired, and/or updated. Consequently, new payment card information isissued to the person and the old payment card information isdeactivated. The new payment card information usually includes a newcard number, a new card expiration date, and/or a new card securitycode. Accordingly, if the person had the old payment card informationpreviously saved on some merchant's computer system, then, in order tomake another purchase through that merchant, the person typically has tomanually enter the new payment card information into that merchant'scomputer system. Although such steps are relatively minimal for a singlemerchant, cumulatively, this process becomes tedious, time consuming,emotionally draining, and/or inconvenient if the person must repeat thisprocess for many merchants. Such process becomes even more tedious, timeconsuming, emotionally draining, and/or inconvenient when performed atdifferent times for different merchants because the user can misplaceand/or forget merchant related sign in information and/or have the newpayment card information stolen, misused, lost, expired, and/or updatedin the interim.

Moreover, the person may not remember every website and/or app thatneeds to be updated and at least with paying bills online, such asutility bills, entertainment bills, and/or others, the person may onlyfind out about providing new payment card information when the merchantcontacts the person for lack of payment. Such state of being hardshipnot only for the person, but also for the merchant who has to dedicateresources for tracking down the customer for the lack of payment and/orensuring that the customer actually pays. Also, such forgetfulness canlead to potential negative impact on the person's credit score.

Although online payment services, such as Paypal®, can somewhat mitigatethe above, many merchants avoid using such services at least due tocompetition, security, added complexity, more computer infrastructure,additional service and/or transaction fees, which cut into themerchants' profits.

BRIEF SUMMARY

The present disclosure may address at least one of the above. However,the present disclosure may also prove useful to other technical areas.Therefore, the claims should not be construed as necessarily limited toaddressing any of the above.

According to an example embodiment of the present disclosure a method isprovided. The method includes maintaining, via a payment card issuercomputer system, first payment card information for a cardholder. Themethod includes processing, via the system, a first card not presenttransaction between the cardholder and a merchant. The first transactionbased at least in part on the first information. The method includesgenerating, via the system, second payment card information for thecardholder. The second information replacing the first information forsubsequent use via the cardholder. The method includes receiving, viathe system, an input from the cardholder. The input indicating themerchant. The input based at least in part on the second informationreplacing the first information. The method includes sending, via thesystem, the second information to the merchant based at least in part onthe input. The method includes processing, via the system, a second cardnot present transaction between the cardholder and the merchant. Thesecond transaction based at least in part on the second informationafter the sending.

According to another example embodiment of the present disclosure amethod is provided. The method includes maintaining, via a payment cardissuer computer system, first payment card information for a cardholder.The first information associated with a transaction history. The methodincludes processing, via the system, a first card not presenttransaction between the cardholder and a merchant. The first transactionbased at least in part on the first information. The history listing thefirst transaction. The method includes generating, via the system,second payment card information for the cardholder. The secondinformation replacing the first information for subsequent use via thecardholder. The method includes selecting, via the system, the merchantfrom the history based at least in part on the first transaction. Theselecting based at least in part on the second information replacing thefirst information. The method includes sending, via the system, thesecond information to the merchant based at least in part on theselecting. The method includes processing, via the system, a second cardnot present transaction between the cardholder and the merchant. Thesecond transaction based at least in part on the second informationafter the sending.

The present disclosure may be embodied in the form illustrated in theaccompanying drawings. However, attention is called to the fact that thedrawings are illustrative. Variations are contemplated as being part ofthe disclosure, limited only by the scope of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate example embodiments of the presentdisclosure. Such drawings are not to be construed as necessarilylimiting the disclosure. Like numbers and/or similar numbering schemecan refer to like and/or similar elements throughout.

FIG. 1 shows an example embodiment of a network diagram according to thepresent disclosure.

FIG. 2A shows an example embodiment of a process for using paymentinformation according to the present disclosure.

FIG. 2B shows an example embodiment of a process for using paymentinformation according to the present disclosure.

FIG. 3 shows an example embodiment of a process for disclosing paymentinformation according to the present disclosure.

FIG. 4 shows an example embodiment of a communication diagram accordingto the present disclosure.

FIG. 5 shows an example embodiment of a process for module operationaccording to the present disclosure.

FIG. 6 shows an example embodiment of a process for receivingnotifications according to the present disclosure.

FIG. 7 shows an example embodiment of a process for disclosing paymentinformation according to the present disclosure.

FIG. 8 shows an example embodiment of a process for handling paymentinformation according to the present disclosure.

FIG. 9 shows an example embodiment of a process for transacting via anew account according to the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present disclosure is now described more fully with reference to theaccompanying drawings, in which example embodiments of the presentdisclosure are shown. The present disclosure may, however, be embodiedin many different forms and should not be construed as necessarily beinglimited to the example embodiments disclosed herein. Rather, theseexample embodiments are provided so that the present disclosure isthorough and complete, and fully conveys the concepts of the presentdisclosure to those skilled in the relevant art. In addition, featuresdescribed with respect to certain example embodiments may be combined inand/or with various other example embodiments. Different aspects and/orelements of example embodiments, as disclosed herein, may be combined ina similar manner. Further, some example embodiments, whetherindividually and/or collectively, may be components of a larger system,wherein other procedures may take precedence over and/or otherwisemodify their application. Additionally, a number of steps may berequired before, after, and/or concurrently with example embodiments, asdisclosed herein. Note that any and/or all methods and/or processes, atleast as disclosed herein, can be at least partially performed via atleast one entity in any manner.

The terminology used herein can imply direct or indirect, full orpartial, temporary or permanent, action or inaction. For example, whenan element is referred to as being “on,” “connected” or “coupled” toanother element, then the element can be directly on, connected orcoupled to the other element and/or intervening elements may be present,including indirect and/or direct variants. In contrast, when an elementis referred to as being “directly connected” or “directly coupled” toanother element, there are no intervening elements present.

Although the terms first, second, etc. may be used herein to describevarious elements, components, regions, layers and/or sections, theseelements, components, regions, layers and/or sections should notnecessarily be limited by such terms. These terms are only used todistinguish one element, component, region, layer or section fromanother element, component, region, layer or section. Thus, a firstelement, component, region, layer, or section discussed below could betermed a second element, component, region, layer, or section withoutdeparting from the teachings of the present disclosure.

The terminology used herein is for describing particular embodimentsonly and is not intended to be necessarily limiting of the presentdisclosure. As used herein, the singular forms “a,” “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. The terms “comprises,” “includes” and/or“comprising,” “including” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. Further, alternate terminology shouldnot be limited necessarily as exclusionary, but can be inclusionary aswell.

Example embodiments of the present disclosure are described herein withreference to illustrations of idealized embodiments (and intermediatestructures) of the present disclosure. As such, variations from theshapes of the illustrations as a result, for example, of manufacturingtechniques and/or tolerances, are to be expected. Thus, the exampleembodiments of the present disclosure should not be construed asnecessarily limited to the particular shapes of regions illustratedherein, but are to include deviations in shapes that result, forexample, from manufacturing.

Unless otherwise defined, all terms used herein, including technical andscientific terms, have the same meaning as commonly understood by one ofordinary skill in the art to which this disclosure belongs. The terms,such as those defined in commonly used dictionaries, should beinterpreted as having a meaning that is consistent with their meaning inthe context of the relevant art and should not be interpreted in anidealized and/or overly formal sense unless expressly so defined herein.

As used herein, the term “about” and/or “substantially” refers to an upto and including a +/−10% variation from the nominal value/term. Suchvariation is always included in any given value/term provided herein,whether or not such variation is specifically referred thereto.

If any disclosures are incorporated herein by reference and suchdisclosures conflict in part and/or in whole with the presentdisclosure, then to the extent of conflict, and/or broader disclosure,and/or broader meaning of terms, the present disclosure controls. Ifsuch disclosures conflict in part and/or in whole with one another, thento the extent of conflict, the later-dated disclosure controls.

FIG. 1 shows an example embodiment of a network environment according tothe present disclosure. An environment 100 includes a network 102, acardholder 104, a card issuer 106, and a merchant 108.

Network 102 includes a plurality of nodes, such as a collection ofcomputers and/or other hardware interconnected by communicationchannels, which allow for sharing of resources and/or information. Suchinterconnection can be direct and/or indirect. Network 102 can be wiredand/or wireless. Network 102 can allow for communication over shortand/or long distances. Network 102 can operate via at least one networkprotocol, such as Ethernet, a Transmission Control Protocol(TCP)/Internet Protocol (IP), and so forth. Network 102 can have anyscale, such as a personal area network, a local area network, a homearea network, a storage area network, a campus area network, a backbonenetwork, a metropolitan area network, a wide area network, an enterpriseprivate network, a virtual private network, a virtual network, asatellite network, a computer cloud network, an internetwork, a cellularnetwork, and so forth. Network 102 can be and/or include an intranetand/or an extranet. Network 102 can be and/or include Internet. Network102 can include other networks and/or allow for communication with othernetworks, whether sub-networks and/or distinct networks, whetheridentical and/or different from network 102. Network 102 can includehardware, such as a network interface card, a repeater, a hub, a bridge,a switch and/or a firewall. Network 102 can be operated, directly and/orindirectly, by and/or on behalf of one and/or more entities,irrespective of any relation to cardholder 104, card issuer 106, and/ormerchant 108.

Network 102 can include a payment card association network, such asVisa® network, MasterCard® network, American Express® network, Discover®network, and others. The payment card association network serves as alink between card issuer 106, which acts on behalf of cardholder 104,and an acquirer, such as an acquiring bank, which acts on behalf ofmerchant 108. An operator of the payment card association network, suchas Visa®, MasterCard®, American Express®, Discover®, and/or others, canset a transaction term for merchant 108, card issuing 106, and/or theacquirer. The payment card association network can be operated by anindependent company and/or one company may operate multiple networks.

Cardholder 104 operates a computer, which can be a hardware and/orsoftware server, a workstation, a desktop, a laptop, a tablet, a mobilephone, a mainframe, a supercomputer, a server farm, and so forth. Thecomputer can be operated, directly and/or indirectly, by and/or onbehalf of cardholder 104. The computer can be touchscreen and/ornon-touchscreen. The computer can include and/or be part of anothercomputer system and/or cloud network. The computer can run any type ofoperating system (OS), such as iOS®, Windows®, Android®, Unix®, Linux®and/or others. The computer can include and/or be coupled to an inputdevice, such as a mouse, a keyboard, a camera, whether forward-facingand/or back-facing, an accelerometer, a touchscreen, and/or amicrophone, and/or an output device, such as a display, a speaker,and/or a printer. The computer is in communication with network 102,such as directly and/or indirectly. Such communication can be via asoftware application, a mobile app, a browser, an OS, and/or anycombination thereof. The computer can include circuitry for globalpositioning determination, such as via a global positioning system(GPS), a signal triangulation system, and so forth. The computer can beequipped with near-field-communication (NFC) circuitry.

Card issuer 106 operates a computer, which can be a hardware and/orsoftware server, a workstation, a desktop, a laptop, a tablet, a mobilephone, a mainframe, a supercomputer, a server farm, and so forth. Thecomputer can be operated, directly and/or indirectly, by and/or onbehalf of card issuer 106. The computer can be touchscreen and/ornon-touchscreen. The computer can include and/or be part of anothercomputer system and/or cloud network. The computer can run any type ofOS, such as iOS®, Windows®, Android®, Unix®, Linux® and/or others. Thecomputer can include and/or be coupled to an input device, such as amouse, a keyboard, a camera, whether forward-facing and/or back-facing,an accelerometer, a touchscreen, and/or a microphone, and/or an outputdevice, such as a display, a speaker, and/or a printer. The computer isin communication with network 102, such as directly and/or indirectly.Such communication can be via a software application, a mobile app, abrowser, an OS, and/or any combination thereof. The computer can includecircuitry for global positioning determination, such as via GPS, asignal triangulation system, and so forth. The computer can be equippedwith NFC circuitry. The computer can run a database, such as arelational database, which contains card issuing information and/orcardholder information.

Merchant 108 operates a computer, which can be a hardware and/orsoftware server, a workstation, a desktop, a laptop, a tablet, a mobilephone, a mainframe, a supercomputer, a server farm, and so forth. Thecomputer can be operated, directly and/or indirectly, by and/or onbehalf of card issuer 106. The computer can be touchscreen and/ornon-touchscreen. The computer can include and/or be part of anothercomputer system and/or cloud network. The computer can run any type ofOS, such as iOS®, Windows®, Android®, Unix®, Linux® and/or others. Thecomputer can include and/or be coupled to an input device, such as amouse, a keyboard, a camera, whether forward-facing and/or back-facing,an accelerometer, a touchscreen, and/or a microphone, and/or an outputdevice, such as a display, a speaker, and/or a printer. The computer isin communication with network 102, such as directly and/or indirectly.Such communication can be via a software application, a mobile app, abrowser, an OS, and/or any combination thereof. The computer can includecircuitry for global positioning determination, such as via GPS, asignal triangulation system, and so forth. The computer can be equippedwith NFC circuitry. The computer can run a database, such as arelational database, which contains payment information.

Cardholder 104 is in communication with network 102, such as direct,indirect, encrypted, unencrypted, and others. Cardholder 104 is inselective communication, such as direct, indirect, encrypted,unencrypted, and others, with at least one of card issuer 106 andmerchant 108 via network 102.

Cardholder 104 includes an individual who makes purchases via a paymentcard. That individual can be a consumer and/or a legal entity, such asan organization, a a company, a partnership, and/or others. Cardholder104 is responsible for charges made onto the payment card.

The payment card includes a card which can be used by cardholder 104 andaccepted by merchant 108 to make a payment for a purchase and/or inpayment of some other obligation. Such purchase and/or obligation can befor a good and/or a service. The payment card includes at least one of acredit card, a debit card, an automatic teller machine (ATM) card, acharge card, a stored-value card, a fleet card, a gift card, a scrip, anelectronic purse, an electronic money wallet, a crypto-currency wallet,a virtual card, and/or others. Note that in some embodiments, a physicalcard may be absent, but a value is associated with the consumer based atleast in part on some form of credit system, such as Hawala. Further,note that the payment card can include any information storage medium,whether physical and/or virtual, such as paper, metal, wood, rubber,computer memory, and/or others. For example, the card can includeplastic items, paper items, metal items, wood items, rubber items, quickresponse (QR) codes depicted on an item, whether physically and/orelectronically, information displayed on electronic mobile devices,wearable computers, and/or others.

Card issuer 106 is in communication with network 102, such as direct,indirect, encrypted, unencrypted, and others. Card issuer 106 is inselective communication, such as direct, indirect, encrypted,unencrypted, and others, with at least one of cardholder 104 andmerchant 108 via network 102. For example, card issuer 106 cancommunicate with the acquirer of merchant 108 regarding merchant 108.Also for example, card issuer 106 can communicate with cardholder 104via email.

Card issuer 106 includes a financial entity, such as a bank, likeChase®, Bank of America®, American Express®, Discover®, TD Bank®, and/orothers, and/or any other organization that issued the payment card tocardholder 104. Card issuer 106 bills cardholder 104 for repayment andbears a risk that the payment card is used fraudulently. Cardholder 104is responsible for repaying after making a purchase via the payment cardissued via card issuer 106. Card issuer 106 can issue an offshorepayment card.

The acquirer includes a financial entity, which accepts and/or processespayment card transactions for merchant 108, including crediting anaccount of merchant 108 for a value charged to the payment card minusany relevant fees. Such accepting and/or processing is for a good and/ora service offered via merchant 108 to cardholder 104.

Merchant 108 is in communication with network 102, such as direct,indirect, encrypted, unencrypted, and others. Merchant 108 is inselective communication, such as direct, indirect, encrypted,unencrypted, and others, with at least one of cardholder 104 and cardissuer 106 via network 102. For example, merchant 108 is incommunication with cardholder 104 via email. Also for example, merchant108 is in communication with card issuer 106 via the acquirer ofmerchant 108. Merchant 108 includes an individual, an organization,and/or a business accepting payment card payments for a good and/or aservice sold to cardholder 104, whether directly and/or indirectly.Merchant 108 includes a for-profit entity, a non-for-profit entity, agovernment agency, and/or others. Merchant 108 includes an onlinemerchant, a brick-and-mortar merchant, and/or any combination thereof.Note that any amount of merchants 108 can be used, as described herein.Note that card issuer 106 can be merchant 108 and/or merchant 108 caninclude card issuer 104. Note that cardholder 104 can be merchant 108and/or merchant 108 can be cardholder 104.

FIG. 2A shows an example embodiment of a process for using paymentinformation according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/or like components described above andany repetitive detailed description thereof will hereinafter be omittedor simplified in order to avoid complication.

A process 200A includes a plurality of blocks 202A-214A. Process 200Acan be performed in sequential numerical order and/or non-sequentialnumerical order. Process 200A is performed via card issuer 106. However,whether domestically and/or internationally, process 200A can beperformed, facilitated for performance, and/or assisted in suchperformance via at least one entity, such as merchant 108, cardholder104, the acquirer of merchant 108, an operator of the credit cardtransaction network, an independent sales organization reselling tomerchant 108 services of the acquirer, an operator of a transactionnetwork which implements electronic payment card transactions, anaffinity partner, such as a retailer, a sports team, a university, acharity, a professional organization, lending its name to card issuer106 for attracting a customer who has a strong relationship with thepartner where the partner get paid a fee/balance percentage for eachcard issued using the partner name, and/or an insurance provider whichunderwriting various insurance protections offered as payment cardperks, such as car rental insurance, hotel burglary insurance, andothers.

In block 202A, card issuer 106 maintains, via a payment card issuercomputer system, first payment card information for cardholder 104. Thesystem can include a server and a database running on the server. Thedatabase contains information for a plurality of cardholders, whichincludes cardholder 104. The first information includes a payment cardnumber, an expiration date, a security code, an operator of the paymentcard association network and/or other relevant information. Suchmaintenance can include at least one of issuing the first information,storage of the first information, securing of the first information fromunauthorized access, sending a bill based at least in part on the firstinformation, storing a transaction history associated with the firstinformation, receiving a payment from cardholder 104 based at least inpart on the first information, and/or other relevant types ofmaintenance. Note that the first information can vary based on paymentcard type.

In block 204A, card issuer 106 processes, via the system, a firsttransaction with merchant 108 based on the first information. The firsttransaction can be a card not present transaction, in which cardholder104 is not in a same locale as merchant 108 during transacting. Suchtransactions include mail order transactions, telephone transactions,facsimile transactions, recurring transaction, and/orInternet/e-commerce transactions. However, note that the firsttransaction can be a card present transaction. The first transaction isbetween at least merchant 108 and cardholder 104. Such processing caninclude communicating with the acquirer, who acts on behalf of merchant108, to facilitate payment to merchant 108 via the acquirer. Suchprocessing can also include billing cardholder 104 based at least inpart on payment to the acquirer and the first information. Suchprocessing can also include receiving payment from cardholder 104 basedon the billing and the first information. The first transaction can be arecurring transaction, an e-commerce transaction, and/or others.

In block 206A, card issuer 106 generates, via the system, second paymentcard information for cardholder 104. Such generation can be manual, suchas via a phone operator of card issuer 106 running a payment informationgeneration program, and/or automatic, such as via receiving anotification that the first information is insecure. The secondinformation includes a payment card number, which can be different fromthe first information, an expiration date, which can be different fromthe first information, a security code, which can be different from thefirst information, an operator of the payment card association network,which can be different from the first information, and/or other relevantinformation. For example, card issuer 106 can issue a new payment cardbased on the second information to cardholder 104. Note that the secondinformation can vary based on payment card type. Although the firstinformation and the second information are for an identical payment cardtype, in some embodiments, the first information can be for a paymentcard of a first type and the second information can be for a paymentcard of a second type different from the first type.

In block 208A, card issuer 106 replaces, via the system, the firstinformation with the second information for subsequent use via thecardholder. Such replacement can occur based at least in part on atleast one of stolen first information, misused first information, lostfirst information, expired first information, updated first information,cardholder 104 request, and/or others. Such replacing can includedeactivating the first information such that the first informationcannot be subsequently used for purchasing.

In block 210A, card issuer 106 receives, via the system, an input fromcardholder 104. The input indicates/implicates merchant 108 sincecardholder 104 already transacted with merchant 108 and there is achance that cardholder 104 will again transact with merchant 108 withthe second information, such as a recurring transaction, a newe-commerce order, and/or others. The input is based at least in part onthe second information replacing the first information, such as afterthe replacing has been noted by card issuer 106. For example, after thereplacing has been confirmed via card issuer 106, cardholder 104 isprovided with the transaction history via the system. Cardholder 104 canbe allowed to provide the input whether based at least in part on thetransaction history associated with the first information and/ormanually entering a merchant identification, such as a name of merchant108 and/or a date of transaction with merchant 108. The input can be viaany input manner, such as a keyboard, a mouse, a microphone, a camera,and/or others. The input can include an alphanumeric text, a voice, animage, a symbol, and/or others. The text can identify merchant 108. Forexample, the text can include at least one of a name of merchant 108, anaddress of merchant 108, an electronic communication information ofmerchant 108, a spent amount of transaction with merchant 108, ageolocation of merchant 108, and a date of transaction with merchant108. The input can be via selecting from a plurality of choices, such asmerchant choices listed in the transaction history associated with thefirst information. The input can via selecting merchant 108 from othermerchants based at least in part on the transaction history. The inputcan be via any element of a graphical user interface provided tocardholder 104 via card issuer 106. Some examples of such elementsinclude a text box, a combo box, a radio button, a check box, a splitbutton, a slider, a list box, a spinner, a drop-down list, a controlmenu, a pie menu, a ribbon, and/or others.

Note that card issuer 106 can maintain, via the system, the transactionhistory associated with the first information. Card issuer 106 canprovide, via the system, a list to cardholder 104. The list includes aplurality of merchants. The merchants include merchant 108. The list isgenerated based at least in part on a computerized analysis of thehistory. The input is via selecting merchant 108 from the merchantsbased at least in part on the list. The analysis is based at least inpart on at least one of a frequency of use, an amount per transaction,and a total amount spent per merchant.

In block 212A, card issuer 106 sends, via the system, the secondinformation to merchant 108 based at least in part on the input. Cardissuer 106 initiates a means of communication by which the secondinformation is sent to merchant 108 without merchant 108 being informedby card issuer 106 of such sending prior to the sending. Although thesending is without merchant 108 specifically requesting for the secondinformation, such configuration can be different in other embodiments.The second information can be send in a direct and/or indirect manner.The second information can be sent in a encrypted and/or unencryptedmanner. For sending, the second information can include alphanumeric,symbolic, audio, video, and/or other types of data. The secondinformation can be sent in an original manner, such as how card issuer106 stores the second information, and/or in a amended manner, such asspecifically formatted manner and/or how merchant 108 desires suchinformation.

Such means of communication can be via any communication technology,including a browser-based email, a client-based email, an instantmessage, a text message, a short message service (SMS), a chat, a voicechat, a web conferencing, a physical snail mail, a telephone, afacsimile, a webpage, a social media post, a social media message, amodule-to-module message, a hypertext transfer protocol (HTTP and/orHTTPS), a file transfer protocol (FTP), and/or any other type of messagesending technology. For example, card issuer 106 can send the secondinformation via the electronic mail to merchant device, such as acomputer and/or phone which is operated by and/or on behalf of merchant108 via the Internet. The second information can include a messageasking merchant 108 to update card holder 104 account on the merchant'scomputer with the updated card information, i.e., the secondinformation. Alternatively, no message is sent along with the secondinformation since by virtue of receiving the second information,merchant 108 can understand that an action to be taken is to update cardholder 104 account on the merchant's computer. In another alternativeembodiment, instead of sending the second information via the electronicmail, a link is sent via the electronic mail for which merchant 108 canclick to access a webpage containing the second information to beretrieved. Alternatively, instead of a link, information directingmerchant 108 to a specific web address/domain name can be sent for whichmerchant 108 can access to retrieve the second information. Further,merchant 108 can submit a preference list to card issuer 106. Thepreference list lists which means of sending is preferred so that cardissuer 106 can send the second information via such preferred means. Thepreference list can be stored in an account on card issuer 106 computereither locally and/or remotely. In addition to communicating the secondinformation to merchant 108, card issuer 106 can simultaneously, orthereafter, inform cardholder 104 that such information is, or has been,sent to merchant 108. Note that the second information can be sent byitself and/or with other information to merchant 108, such as the secondinformation for other cardholders 104, general information, technicalinformation, non-payment information for other cardholders 104, and/orothers.

In block 214A, card issuer 106 processes, via the system, a secondtransaction with merchant 108 based on the second information after thesending. The second transaction can be a card not present transaction inwhich cardholder 104 is not in a same locale as merchant 108 duringtransacting. Such transactions include mail order transactions,telephone transactions, facsimile transactions, recurring transaction,and/or Internet/e-commerce transactions. However, second transaction canbe a card present transaction. The second transaction is between atleast merchant 108 and cardholder 104. Such processing can includecommunicating with the acquirer, who acts on behalf of merchant 108, tofacilitate payment to merchant 108 via the acquirer. Such processing canalso include billing cardholder 104 based at least in part on payment tothe acquirer and the second information. Such processing can alsoinclude receiving payment from cardholder 104 based on the billing andthe second information. The second transaction can be a recurringtransaction, an e-commerce transaction, and/or others. The secondtransaction and the first transaction can relate to identical subjectmatter and/or be non-related.

For example, cardholders 104 purchase goods and/or services online frommerchants 108, such as Amazon®, Target®, and others. Such purchases aretypically made, whether via merchants' 108 websites and/or mobile apps,using payment card information, such as credit card information and/ordebit card information. In order to make such shopping experiencesimpler, many merchants 108 optionally allow for the payment cardinformation to be saved on merchants' 108 computer systems for futureuse. Therefore, based on cardholders' 104 signing-in into merchants' 108systems, such as via provision of an email address and/or a password,the payment card information is readily available for authorizingpayment. However, often, cardholder 104 payment card information, suchas the first information, is stolen, misused, lost, expired, and/orupdated. Consequently, new payment card information, such as the secondinformation, is issued to cardholder 104 and the old payment cardinformation, such as the first information, is deactivated. The newpayment card information, such as the second information, usuallyincludes a new card number, a new card expiration date, and/or a newcard security code. Accordingly, if cardholder 104 had the old paymentcard information, such as the first information, previously saved onmerchant 108 computer system, then, in order to make another purchasethrough that merchant 108, cardholder 104 typically has to manuallyenter the new payment card information, such as the second information,into that merchant's 108 computer system. Although such steps arerelatively minimal for a single merchant 108, cumulatively, this processbecomes tedious, time consuming, emotionally draining, and/orinconvenient if cardholder 104 must repeat this process for manymerchants 108. Such process becomes even more tedious, time consuming,emotionally draining, and/or inconvenient when performed at differenttimes for different merchants 108 because cardholder 104 can misplaceand/or forget merchant 108 related sign in information and/or have thenew payment card information, such as the second information, stolen,misused, lost, expired, and/or updated in the interim. Moreover,cardholder 104 may not remember every website and/or app that needs tobe updated and at least with paying bills online, such as utility bills,entertainment bills, and/or others, cardholder 104 may only find outabout providing new payment card information when merchant 108 contactscardholder 104 for lack of payment. Such state of being hardship notonly for cardholder 104, but also for merchant 108 who has to dedicateresources for tracking down cardholder 104 for the lack of paymentand/or ensuring that cardholder 104 actually pays. Also, suchforgetfulness can lead to potential negative impact on cardholder 104credit score. Therefore, via cardholder 104 accessing card issuer 106 tosend the new payment information, such as the second paymentinformation, to merchant 108, cardholder 104 avoids manually enteringthe new payment information, such as the second information, intomerchants 108 computer systems, while effectively saving time in aconvenient manner, even if the new payment card information, such as thesecond information, stolen, misused, lost, expired, and/or updated inthe interim. Further, cardholder 104 effectively avoids every websiteand/or app that needs to be updated and at least with paying billsonline, such as utility bills, entertainment bills, and/or others.Likewise, merchant 108 can effectively avoid dedicating resources fortracking down cardholder 104 for the lack of payment and/or ensuringthat cardholder 104 actually pays. Moreover, cardholder 104 can avoidsuch forgetfulness leading to potential negative impact on cardholder104 credit score. Consequently, such technology effectively reduces aneed for cardholder 104 to visit multiple merchant websites and updatepayment information on those sites piecemeal. In some embodiments, inorder to reduce a likelihood of sensitive information, such as thesecond information, being intercepted, card issuer 106 sends the secondinformation when cardholder 104 accesses card issuer 106 to updatepayment information for merchant 108.

FIG. 2B shows an example embodiment of a process for using paymentinformation according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/or like components described above andany repetitive detailed description thereof will hereinafter be omittedor simplified in order to avoid complication.

A process 200B includes a plurality of blocks 202B-216B. Process 200Bcan be performed in sequential numerical order and/or non-sequentialnumerical order. Process 200B is performed via card issuer 106. However,whether domestically and/or internationally, process 200B can beperformed, facilitated for performance, and/or assisted in suchperformance via at least one entity, such as merchant 108, cardholder104, the acquirer of merchant 108, an operator of the credit cardtransaction network, an independent sales organization reselling tomerchant 108 services of the acquirer, an operator of a transactionnetwork which implements electronic payment card transactions, anaffinity partner, such as a retailer, a sports team, a university, acharity, a professional organization, lending its name to card issuer106 for attracting a customer who has a strong relationship with thepartner where the partner get paid a fee/balance percentage for eachcard issued using the partner name, and/or an insurance provider whichunderwriting various insurance protections offered as payment cardperks, such as car rental insurance, hotel burglary insurance, andothers.

In block 202B, card issuer 106 maintains, via the system, the firstinformation cardholder 104, as described herein. The first informationis associated with the transaction history listing transactions betweencardholder 104 and other merchants 108.

In block 204B, card issuer 106 processes, via the system, the firsttransaction between cardholder 104 and merchant 108, as describedherein. The first transaction is based at least in part on the firstinformation, such as charged according to the first information.

In block 206B, card issuer 106 stores, via the system, information aboutthe first transaction in the transaction history, as described herein.The transaction history is for the first information such that thetransaction history lists the first transaction.

In block 208B, card issuer 106 generates, via the system, the secondinformation for cardholder 104, as described herein.

In block 210B, card issuer 106 replaces, via the system, the firstinformation with the second information, as described herein.

In block 212B, card issuer 106 selects, via the system, merchant 108from the transaction history based at least in part on the firsttransaction. The selecting indicates/implicates merchant 108 sincecardholder 104 already transacted with merchant 108 and there is achance that cardholder 104 will again transact with merchant 108 withthe second information, such as a recurring transaction, a newe-commerce order, and/or others. The selecting is done manually, such asvia an employee of card issuer 106, and/or automatically, via a computerprogram, which analyzes the transaction history for who to select in thehistory. Such analysis can be heuristic, deterministic, and/or others.Such analysis can be based at least in part on at least one of afrequency of use, such as how frequently has merchant 108 transactedwith cardholder 106 for a selected time period in relation to othermerchants listed in the transaction history, an amount per transaction,such as an average amount per transaction between cardholder 104 andmerchant 108 in relation to other merchants listed in the transactionhistory, and a total amount spent per merchant, such as how much ascardholder 104 transacted with merchant 108 in relation to othermerchants listed in the transaction history. The selecting is based atleast in part on the second information replacing the first information,such as after the replacing has been noted by card issuer 106. Forexample, after the replacing has been confirmed via card issuer 106,selects merchant 108 based on the analysis above. The selecting can bevia any selecting manner, such as a keyboard, a mouse, a microphone, acamera, and/or others. The selecting can include an alphanumeric text, avoice, an image, a symbol, and/or others. The selecting can be viaselecting from a plurality of choices, such as merchant choices listedin the transaction history associated with the first information. Theselecting can be via any element of a graphical user interface providedto cardholder 104 via card issuer 106. Some examples of such elementsinclude a text box, a combo box, a radio button, a check box, a splitbutton, a slider, a list box, a spinner, a drop-down list, a controlmenu, a pie menu, a ribbon, and/or others.

For example, card issuer 106 can computationally analyze the transactionhistory and generate a report based at least in part on such analysis.Such analysis can be based at least in part on at least one of afrequency of use, such as how frequently has merchant 108 transactedwith cardholder 106 for a selected time period in relation to othermerchants listed in the transaction history, an amount per transaction,such as an average amount per transaction between cardholder 104 andmerchant 108 in relation to other merchants listed in the transactionhistory, and a total amount spent per merchant, such as how much ascardholder 104 transacted with merchant 108 in relation to othermerchants listed in the transaction history. Resultantly, the reportcontains a list of merchants, which includes merchant 108. Card issuer106 then provides the report, such as via a webpage, to cardholder 104for review, such as via accessing the system of card issuer 106.Cardholder 104 can review the report and fully confirm, fullydisconfirm, partially confirm, and/or partially disconfirm whichmerchants mentioned in the report that cardholder 104 desires to sendthe second information to. When cardholder 104 confirms at leastmerchant 108 during such review, then card issuer 106 sends the secondinformation to merchant 108.

In block 214B, card issuer 106 sends, via the system, the secondinformation to merchant 108 based at least in part on the selecting, asdescribed herein.

In block 216B, card issuer 106 processes, via the system, a second cardnot present transaction between cardholder 104 and merchant 108, asdescribed herein. The second transaction is based at least in part onthe second information after the sending.

For example, cardholder 104 can manually select from the list and/orinform card issuer 106 which merchants 108 will receive the secondinformation. The list can be obtained from card issuer 106. The listincludes merchants 108 from which cardholder 104 previously purchaseditems/services from using the first information. Cardholder 104 can alsoselect, based on merchant selection algorithms, for card issuer 106 toautomatically select merchants, such as merchant 108, based on variouscriteria, such as prior spending history, most frequently used merchantsbased one or more time periods, money spent and/or every merchant everused. Upon selecting merchant(s) to which to send the secondinformation, such as merchant 108, card issuer 106 sends datarepresenting the second information to the merchant(s). Such data caninclude personal identifying information, which may be just the secondpayment information, contact information, personal identificationinformation and/or first payment information for identifying the user onthe merchant(s) computer system and/or any combination thereof. Uponreceiving such data, whether immediately or after some time period, themerchant(s) associates, whether manually and/or automatically, thesecond information with cardholder 104 account at the merchant(s)computer system. Alternatively, the information is updated on merchant'send without merchant involvement and/or input.

In other embodiments, process 200B includes receiving, via the system, amessage from merchant 108. The message confirming a receipt of thesecond information based at least in part on the sending. Process 200Bfurther includes receiving, via the system, a message from merchant 108.The message confirming a storage of second information on a storagemedium associated with merchant 108, such as owned via merchant 108.Process 200B further includes providing a software module via cardissuer 106 to merchant 108 before the sending. The module is configuredfor receiving the second information based at least in part on thesending. Process 200B further includes receiving, via the system, aninput from cardholder 104. The input modifying a selection of merchant108 based at least in part on the selecting. For example, if, based onthe computerized analysis, the system provided a list of merchants, withmerchant 108 therein, to cardholder 104 and cardholder 104 desires tomodify that list, such as via adding merchants thereto and/or removingmerchants therefrom, then cardholder 104 can provide the input into thesystem to modify the list. However, if cardholder 104 is happy withcontents of the list, then the system can receive an input fromcardholder 104, which confirms the selecting. Note that cardholder 104can elect other merchants, such as via checking off correspondingcheckboxes in the transaction history and/or the list, who were notselected via the system. Such electing allows card issuer 106 to sendthe second information to those merchants.

FIG. 3 shows an example embodiment of a process for disclosing paymentinformation according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/Attorney or like components describedabove and any repetitive detailed description thereof will hereinafterbe omitted or simplified in order to avoid complication.

A process 300 includes a plurality of blocks 302-306. Process 300 can beperformed in sequential numerical order and/or non-sequential numericalorder. Process 300 is performed via cardholder 104. However, whetherdomestically and/or internationally, process 300 can be performed,facilitated for performance, and/or assisted in such performance via atleast one entity, such as merchant 108, card issuer 106, the acquirer ofmerchant 108, an operator of the credit card transaction network, anindependent sales organization reselling to merchant 108 services of theacquirer, an operator of a transaction network which implementselectronic payment card transactions, an affinity partner, such as aretailer, a sports team, a university, a charity, a professionalorganization, lending its name to card issuer 106 for attracting acustomer who has a strong relationship with the partner where thepartner get paid a fee/balance percentage for each card issued using thepartner name, and/or an insurance provider which underwriting variousinsurance protections offered as payment card perks, such as car rentalinsurance, hotel burglary insurance, and others.

In block 302, cardholder 104 accesses the system of card issuer 106.Such accessing can be in any manner, whether secure and/or insecure,whether direct and/or indirect. For example, cardholder 104 can operatethe computer of cardholder 104 and, over network 102, securely sign-ininto the system of card issuer 104. In other embodiments, such accesscan be over phone, email, facsimile, in-person, social media, texting,messaging, chat, and/or others.

In block 302, cardholder 104 indicates merchant 108. Such indicationallows cardholder 104 to select to which merchant 108 should card issuer106 send the second information for subsequent use, which can beimmediate. Such indication can be via textual, voice, image, symbolicand/or any other input. Such indication can be via cardholder 104selecting merchant 108 from the transaction history. Such indication canbe via cardholder 104 selecting merchant 108 from a list provided tocardholder 104 via card issuer 106 based at least in part on card issuer106 analyzing the transaction history for various trends of cardholder104.

In block 306, cardholder 104 authorizes card issuer 106 to send thesecond information from card issuer 106 to merchant 108. Suchauthorization can be via any manner, such as via a message prompt, acheckbox, and others. The authorization is requested, via the system.Note that in other embodiments, card issuer 106 sends the secondinformation without authorization of cardholder 104.

FIG. 4 shows an example embodiment of a communication diagram accordingto the present disclosure. Some elements of this figure are describedabove. Thus, same and/or similar reference characters identify identicaland/or like components described above and any repetitive detaileddescription thereof will hereinafter be omitted or simplified in orderto avoid complication.

Card issuer 406 provides a software module 410 to merchant 408 beforecard issuer 406 sends the second information to merchant 408. Module 410configured for receiving the second information based at least in parton the sending of the second information via card issuer 406. Forexample, module 410 can communicate with the system of card issuer 406.

Note that module 410 is an example and card issuer 406 can providemerchant 408 with any logic, whether hardware, like a chip and/orcircuitry, and/or software, like a software patch, a piece of code,and/or a program and/or any combination thereof. In some embodiments,the logic can be operative for retrofitting preexisting hardware and/orsoftware on merchant's 408 end, irrespective of whether such hardwareand/or software is merchant 408 specific, or be a new feature on themerchant's 408 end. This logic can provide for standardization ofperformance of such process for any, many and/or all merchants capableof payment processing according to the second information. The logic canallow for seamless updating of the second information data on thebackend between card issuer 406 and merchants 408. The logic can includeand/or allow for security measures, such as encryption, user questions,image matching, automated phone call, emails, text messages, card issuer406 staff call and/or any combination thereof. The measures can bebetween cardholder 104 and card issuer 406 and/or card issuer 406 andmerchant(s) 408. The logic and/or card issuer 406 independent of thelogic can display a message confirming update of the second informationwhen card issuer 406 accesses merchant 408(s) system(s).

In an embodiment, when cardholder 104 has at least two paymentinformation accounts with one card issuer 406 accessible via one login,then cardholder 104 can send at least one of the at least two paymentaccount data to merchant 408(s), as described herein. For example,cardholder 104 has credit cards X and Y accessible via one login at cardissuer 406. Credit card X has been used more frequently than credit cardY as believed by cardholder 104. Cardholder 104 can access card issuer406 to authorize card issuer 406 to transmit credit card data for X andY to merchant(s) 408 that have charged either credit card so that eachcredit card information is accessible to merchant 408 that have chargedthe other card. For example, if card X has been used at merchants A, Band C and card Y has been used by A, B, D and E, then cardholder 104 canauthorize card issuer 406 to transmit card X data to D and/or E and cardY data to C.

FIG. 5 shows an example embodiment of a process for module operationaccording to the present disclosure. Some elements of this figure aredescribed above. Thus, same and/or similar reference characters identifyidentical and/or like components described above and any repetitivedetailed description thereof will hereinafter be omitted or simplifiedin order to avoid complication.

A process 500 includes a plurality of blocks 502-514. Process 500 can beperformed in sequential numerical order and/or non-sequential numericalorder. Process 500 is performed via merchant 408. However, whetherdomestically and/or internationally, process 500 can be performed,facilitated for performance, and/or assisted in such performance via atleast one entity, such as cardholder 104, card issuer 406, the acquirerof merchant 108, an operator of the credit card transaction network, anindependent sales organization reselling to merchant 108 services of theacquirer, an operator of a transaction network which implementselectronic payment card transactions, an affinity partner, such as aretailer, a sports team, a university, a charity, a professionalorganization, lending its name to card issuer 106 for attracting acustomer who has a strong relationship with the partner where thepartner get paid a fee/balance percentage for each card issued using thepartner name, and/or an insurance provider which underwriting variousinsurance protections offered as payment card perks, such as car rentalinsurance, hotel burglary insurance, and others.

In block 502, merchant 408 receives module 410 from card issuer 406.Such receipt can be via any manner, whether physically and/orelectronically. For example, such receipt can be via email, chat, filetransfer, a physically mailed computer memory with module 410 thereon,source code, texting, multimedia messaging, a payment systemupdate/upgrade, and/or others.

In block 504, merchant 408 installs module 410. Such installationdepends on how module 410 was provided. For example, a self-extractingmodule 410 can be executed via merchant 408 and self-installed onto thepayment system of merchant 408. Also for example, module 410 can beinstalled via an update/upgrade to the payment system of merchant 408.

In block 506, merchant 408 stores the first information in the paymentsystem, as described herein. Note that block 506 can occur before block502 and/or block 504.

In block 508, merchant 408 transacts with cardholder 106 based at leastin part on the first information, as described herein. Note that block506 can occur after block 508.

In block 510, merchant 408 receives the second information from cardissuer 406 via module 410. Such receipt can be wired and/or wireless.Such receipt can be direct and/or indirect. Such receipt can beencrypted and/or unencrypted. Note that the second information can besent en masse for a set of cardholders 104.

In block 512, merchant 408 stores the second information in the paymentsystem. The payment system retrieves the second information from module410 for storing in the payment system. The payment system can delete thesecond information from module 410 for security purposes after suchretrieval. Module 410 can also be configured to self-delete the secondinformation upon retrieval confirmation. Module 410 can also beconfigured to delete such information upon receiving a command from cardissuer 406, which can be periodic. Module 410 can also be configured tocontain a linked list, a stack, and/or a queue for retrieval of thesecond information in a first-in-first-out (FIFO) and/orfirst-in-last-out (FILO) manner. Module 410 can also be configured todecrypt the second payment information before provision to the paymentsystem when the second information is encrypted via card issuer 406 atleast before sending to module 410. Alternatively, module 410 sends thesecond information to the payment system immediately upon receipt of thesecond information from card issuer 406 and then self-deletes the secondinformation upon receipt confirmation from the payment system.

In block 514, merchant 408 transacts with cardholder 104 based at leastin part on the second information, as described herein.

FIG. 6 shows an example embodiment of a process for receivingnotifications according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/or like components described above andany repetitive detailed description thereof will hereinafter be omittedor simplified in order to avoid complication.

A process 600 includes a plurality of blocks 602-608. Process 600 can beperformed in sequential numerical order and/or non-sequential numericalorder. Process 600 is performed via card issuer 106. However, whetherdomestically and/or internationally, process 600 can be performed,facilitated for performance, and/or assisted in such performance via atleast one entity, such as cardholder 104, merchant 108, the acquirer ofmerchant 108, an operator of the credit card transaction network, anindependent sales organization reselling to merchant 108 services of theacquirer, an operator of a transaction network which implementselectronic payment card transactions, an affinity partner, such as aretailer, a sports team, a university, a charity, a professionalorganization, lending its name to card issuer 106 for attracting acustomer who has a strong relationship with the partner where thepartner get paid a fee/balance percentage for each card issued using thepartner name, and/or an insurance provider which underwriting variousinsurance protections offered as payment card perks, such as car rentalinsurance, hotel burglary insurance, and others.

In block 602, card issuer 104 sends, via the system, the secondinformation to merchant 108, as described herein.

In block 604, card issuer 104 receives, via the system, a receiptnotification message from merchant 108. The message confirms a receiptof the second information based at least in part on the sending. Themessage can be sent from merchant 108 via module 410. The message can besent from merchant 108 via another communication means, such as email,fax, texting, chatting, file transfer, facsimile, physical letter,and/or others.

In block 606, card issuer 104 receives, via the system, a storagenotification message from merchant 108. The message confirms a storageof the second information based at least in part on the sending. Themessage can be sent from merchant 108 via module 410. The message can besent via the payment system of merchant 108. The message can be sentfrom merchant 108 via another communication means, such as email, fax,texting, chatting, file transfer, facsimile, physical letter, and/orothers. The storage of the second information on a storage mediumassociated with merchant 108. The storage medium can be digital and/oranalog. For example, the storage medium can include computer memory,paper records, and/or others.

In block 608, card issuer 104 facilitates transacting between cardholder104 and merchant 108 based at least in part on the second information,as described herein. For example, such facilitation can includeprocessing the second transaction with merchant 108 based at least inpart on the second information.

FIG. 7 shows an example embodiment of a process for disclosing paymentinformation according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/or like components described above andany repetitive detailed description thereof will hereinafter be omittedor simplified in order to avoid complication.

A process 700 includes a plurality of blocks 702-710. Process 700 can beperformed in sequential numerical order and/or non-sequential numericalorder. Process 700 is performed via card issuer 106. However, whetherdomestically and/or internationally, process 700 can be performed,facilitated for performance, and/or assisted in such performance via atleast one entity, such as cardholder 104, merchant 108, the acquirer ofmerchant 108, an operator of the credit card transaction network, anindependent sales organization reselling to merchant 108 services of theacquirer, an operator of a transaction network which implementselectronic payment card transactions, an affinity partner, such as aretailer, a sports team, a university, a charity, a professionalorganization, lending its name to card issuer 106 for attracting acustomer who has a strong relationship with the partner where thepartner get paid a fee/balance percentage for each card issued using thepartner name, and/or an insurance provider which underwriting variousinsurance protections offered as payment card perks, such as car rentalinsurance, hotel burglary insurance, and others.

In block 702, card issuer 106 generates the second information, asdescribed herein.

In block 704, card issuer 106 provides the transaction history for thefirst information to cardholder 104, as described herein. Such provisionis visual, but can be auditory, alphanumeric, symbolic, and others. Forexample, such provision can be via a liquid crystal display (LCD). Suchprovision can be requested via cardholder 104 from card issuer 106, suchas via a webpage. Such provision can be mandated onto cardholder 104 viacard issuer 106, such as via a webpage.

In block 706, card issuer 106 selects merchant 108 from the transactionhistory based at least in part on computerized analysis of thetransaction history, as described herein. Note that card issuer 106 canalso select no merchants at all. Further, note that card issuer 106 canselect a plurality of merchants, which can include merchant 108. Themerchants can be ranked/rated, as described herein. Note that suchrankings/ratings can be selectively sorted via cardholder 104.

In block 708, card issuer 106 receives authorization from cardholder 104to send the second information to merchants, which can include merchant108, as selected via card issuer 106 and/or cardholder 104. Suchauthorization can be biometric, alphanumeric, symbolic, and others. Suchauthorization can be via any visual and/or communication means describedherein.

In block 710, card issuer 106 facilitates transacting between cardholder104 and merchant 108 based at least in part on the second information,as described herein. For example, such facilitation can includeprocessing the second transaction with merchant 108 based at least inpart on the second information.

FIG. 8 shows an example embodiment of a process for handling paymentinformation according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/or like components described above andany repetitive detailed description thereof will hereinafter be omittedor simplified in order to avoid complication.

A process 800 includes a plurality of blocks 802-810. Process 800 can beperformed in sequential numerical order and/or non-sequential numericalorder. Process 800 is performed via merchant 108. However, whetherdomestically and/or internationally, process 800 can be performed,facilitated for performance, and/or assisted in such performance via atleast one entity, such as cardholder 104, card issuer 106, the acquirerof merchant 108, an operator of the credit card transaction network, anindependent sales organization reselling to merchant 108 services of theacquirer, an operator of a transaction network which implementselectronic payment card transactions, an affinity partner, such as aretailer, a sports team, a university, a charity, a professionalorganization, lending its name to card issuer 106 for attracting acustomer who has a strong relationship with the partner where thepartner get paid a fee/balance percentage for each card issued using thepartner name, and/or an insurance provider which underwriting variousinsurance protections offered as payment card perks, such as car rentalinsurance, hotel burglary insurance, and others.

In block 802, merchant 108 maintains a customer account of cardholder104. Merchant 108 stores the first information in the account. Forexample, such maintenance can include securing access to the account,storing transaction data for the account, and others.

In block 804, merchant 108 receives the second information from cardissuer 106, as described herein.

In block 806, merchant 108 matches the second information to thecustomer account. The matching occurs via the payment system based atleast in part on receiving the second information from module 410. Thematching can be one-to-one correspondence, one-to-many correspondence,many-to-many correspondence, and/or many-to-one correspondence. Thematching can be based on precise matching and/or imprecise matching,such as accounting for capital alphanumeric characters. The matching canbe statistical, heuristic and/or deterministic based. For example, when,in addition to actual payment data, the second information includes atleast one of the customer account data, cardholder 104 personalidentification data, cardholder 104 contact information data, and otherdata relevant to matching to the customer account, then merchant 108uses such data to match to the customer account.

In block 808, merchant 108, based at least in part on successfulmatching, such as via identifying the account of cardholder 104 atmerchant 108 based at least on part data received from card issuer 106,associates the second information with the account for subsequentcharging according thereto. For example, such association can includemaintaining, as described herein. Also for example, such association caninclude storing the second information in the account and replacing thefirst information in the account with the second information. Merchant108 can delete the first information from the account and/or choose tokeep in the account for documentation/trail/security purposes. Note thatthe first information can be visible to cardholder 104 and/or invisibleto cardholder 104, whether selectively via merchant 108 and/orcardholder 104.

In block 810, merchant 108 transacts with cardholder 104 based at leastin part on the second information, as described herein. The secondinformation is stored in the account.

FIG. 9 shows an example embodiment of a process for transacting via anew account according to the present disclosure. Some elements of thisfigure are described above. Thus, same and/or similar referencecharacters identify identical and/or like components described above andany repetitive detailed description thereof will hereinafter be omittedor simplified in order to avoid complication.

A process 900 includes a plurality of blocks 902-908. Process 900 can beperformed in sequential numerical order and/or non-sequential numericalorder. Process 900 is performed via merchant 108. However, whetherdomestically and/or internationally, process 900 can be performed,facilitated for performance, and/or assisted in such performance via atleast one entity, such as cardholder 104, card issuer 106, the acquirerof merchant 108, an operator of the credit card transaction network, anindependent sales organization reselling to merchant 108 services of theacquirer, an operator of a transaction network which implementselectronic payment card transactions, an affinity partner, such as aretailer, a sports team, a university, a charity, a professionalorganization, lending its name to card issuer 106 for attracting acustomer who has a strong relationship with the partner where thepartner get paid a fee/balance percentage for each card issued using thepartner name, and/or an insurance provider which underwriting variousinsurance protections offered as payment card perks, such as car rentalinsurance, hotel burglary insurance, and others.

In block 902, merchant 108 receives payment card information forcardholder 104 from card issuer 106, such as over network 102. Suchreceipt is as described herein. For example, such receipt can be viamodule 410 and/or the logic. Such information can include actual paymentdata, such as payment card number, expiration date, security code, andothers. Note that such data can vary based at least in part on paymentcard type. Such payment data can include cardholder 104 personalidentification data, cardholder 104 contact information data, shippingdata, and other cardholder 104 identifying data, such as biometrics.

In block 904, merchant 108 creates a new customer account based on thereceived payment card information 408. Merchant 108 can communicate withcard issuer 106, such as via the acquirer, via network 102, and/orothers, to verify validity of the payment information data, checkcreditworthiness of cardholder 104, and confirm payment data sufficiencyto charge cardholder 104 accordingly. Note that merchant 108 can alsoaccess other entities for such verification, such as a credit scorebureau.

When cardholder 104 already has a duplicate/preexisting account withmerchant 108, then merchant 108 can mandate for account joining andupdating payment information for latest payment information, as receivedin block 902 and as described herein, and/or keep theduplicate/preexisting account separate. Merchant 108 can also requestcardholder 104 via the preexisting account, such as via email, phone,text, and/or others, how cardholder 104 wants merchant 108 to proceedwhen a new account would be created. When the duplicate/preexistingaccounts are kept separately, then merchant 108 can synchronize both ofthem based at least in part on latest payment data such that bothaccounts can be transacted therethrough equally. Also, suchsynchronization can allow for contact information synchronization, suchas address synchronization, and/or signing-in informationsynchronization, such as email and password synchronization, which canbe used if cardholder 104 forgot and/or misplaced such information.Alternatively, when the duplicate/preexisting accounts are keptseparately, then merchant 108 can allow for non-synchronization andkeeping both accounts totally separately where the first account remainsas is. Note that merchant 108 can request for advice from cardholder 104on a course of action when faced with the duplicate/preexisting account.

In block 906, merchant 108 enables cardholder 104 to access the account.Such enabling is based at least in part on successful verification thatthe received payment information data is valid, cardholder 104 iscreditworthy, and cardholder 104 can be charged according to thereceived payment information, such as payment sufficiency. Such enablingincludes configuring merchant 108 computer system for transacting,notifying cardholder 104 of successful account creation, providing logindata for cardholder 104, and others. Resultantly, cardholder 104 canaccess merchant 108 via the account to transact according to the paymentcard information. Cardholder 104 can access the account without havingto later input payment card information prior to, for example,purchasing an item and/or paying for a service at merchant 108.

In block 908, merchant 108 transacts with cardholder 104 based at leastin part on the received payment information, as described herein. Thereceived payment information is stored in the account.

In other embodiments, for greater security/fraud reduction, card issuer106 can review/rate merchants 108, such as on a pass/fail scale, atiered scale, and/or others. Such review/rating is based at least inpart on internal data and/or external data. Such review/rating is basedat least in part on security criteria, fraud criteria, and/or customerservice reputation criteria. Then, card issuer 106 can allow cardholder104 to select for sending of the second information only to thosemerchants 108 who card issuer 106 approves based at least in part onsuch review/rating.

In other embodiments, the sending of the second information can be donefrom one card issuer 106 to another card issuer 106 when cardholder 104desires that the latter card issuer 106 should be aware of paymentinformation of the former card issuer 106, whether or not, cardholder104 transacted with the latter card issuer 106 via the former cardissuer 106.

Aspects of the present disclosure may be embodied as a system, a method,and/or a computer program product. Accordingly, some implementations ofthe present disclosure may be embodied in an entirely hardwareembodiment, an entirely software embodiment (including firmware,resident software, micro-code, and so forth) and/or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,some implementations of the present disclosure may take the form of acomputer program product embodied in at least one computer readablemedium having computer readable program code embodied thereon. Anycombination of one or more computer readable medium(s) may be utilized.The computer readable medium may be a computer readable signal medium ora computer readable storage medium (including, but not limited to,non-transitory computer readable storage media). A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of the present disclosure, a computer readablestorage medium may be any tangible medium that can contain, or store aprogram for use by or in connection with an instruction executionsystem, apparatus, and/or device. A computer readable signal medium mayinclude a propagated data signal with computer readable program codeembodied therein, for example, in baseband or as part of a carrier wave.Such a propagated signal may take any of a variety of forms, including,but not limited to, electro-magnetic, optical, or any suitablecombination thereof. A computer readable signal medium may be anycomputer readable medium that is not a computer readable storage mediumand that can communicate, propagate or transport a program for use byand/or in connection with an instruction execution system, an apparatusand/or a device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wired, optical fiber cable, radio frequency, and so forth, or anysuitable combination of the foregoing. Computer program code forcarrying out operations for aspects of the present disclosure may bewritten in any combination of one or more programming languages,including an object oriented programming language, such as Java,Smalltalk, C#, C++ or the like, and procedural programming languages,such as the “C” programming language or similar programming languages.The program code may execute entirely on the user's computer, partly onthe user's computer, as a stand-alone software package, partly on theuser's computer and partly on a remote computer or entirely on theremote computer or server. In the latter scenario, the remote computermay be connected to the user's computer through any type of network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made to an external computer (for example, throughthe Internet using an Internet Service Provider).

Aspects of the present disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. Each block of the flowchart illustrations and/or blockdiagrams, and combinations of blocks in the flowchart illustrationsand/or block diagrams, can be implemented by computer programinstructions. These computer program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks. The computer program instructions may also beloaded onto a computer, other programmable data processing apparatus, orother devices to cause a series of operational steps to be performed onthe computer, other programmable apparatus or other devices to produce acomputer implemented process such that the instructions which execute onthe computer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). Note that, in somealternative implementations, the functions noted in the block may occurout of the order noted in the figures. For example, two blocks shown insuccession may be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. Each block of the block diagrams and/orflowchart illustration, and combinations of blocks in the block diagramsand/or flowchart illustration can be implemented by special purposehardware-based systems that perform the specified functions or acts, orcombinations of special purpose hardware and computer instructions. Theflow diagrams depicted herein are just one example. There may be manyvariations to this diagram or the steps (or operations) describedtherein without departing from the spirit of the disclosure. Forinstance, the steps may be performed in a differing order or steps maybe added, deleted, and/or modified. All of these variations areconsidered a part of the claimed disclosure.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed.

The description of the present disclosure has been presented forpurposes of illustration and description, but is not intended to befully exhaustive and/or limited to the disclosure in the form disclosed.Many modifications and variations in techniques and structures areapparent to those of ordinary skill in the art without departing fromthe scope and spirit of the disclosure as set forth in the claims thatfollow. Accordingly, such modifications and variations are contemplatedas being a part of the present disclosure. The scope of the presentdisclosure is defined by the claims, which includes known equivalentsand unforeseeable equivalents at the time of filing of the presentdisclosure.

What is claimed is:
 1. A method comprising: maintaining, via a paymentcard issuer computer system, first payment card information for acardholder; processing, via said system, a first card not presenttransaction between said cardholder and a merchant, said firsttransaction based at least in part on said first information;generating, via said system, second payment card information for saidcardholder, said second information replacing said first information forsubsequent use via said cardholder; receiving, via said system, an inputfrom said cardholder, said input indicating said merchant, said inputbased at least in part on said second information replacing said firstinformation; sending, via said system, said second information to saidmerchant based at least in part on said input; processing, via saidsystem, a second card not present transaction between said cardholderand said merchant, said second transaction based at least in part onsaid second information after said sending.
 2. The method of claim 1,further comprising: receiving, via said system, a message from saidmerchant, said message confirming a receipt of said second informationbased at least in part on said sending.
 3. The method of claim 1,further comprising: receiving, via said system, a message from saidmerchant, said message confirming a storage of said second informationon a storage medium associated with said merchant.
 4. The method ofclaim 1, further comprising: providing, via said system, a transactionhistory to said cardholder, said history associated with said firstinformation, said input via selecting said merchant based at least inpart on said history.
 5. The method of claim 1, wherein said inputincludes an alphanumeric text.
 6. The method of claim 1, furthercomprising: maintaining, via said system, a transaction historyassociated with said first information; providing, via said system, alist to said cardholder, said list including a plurality of merchants,said merchants including said merchant, said list generated based atleast in part on a computerized analysis of said history, said input viaselecting said merchant from said merchants based at least in part onsaid list.
 7. The method of claim 6, wherein said analysis is based atleast in part on at least one of a frequency of use, an amount pertransaction, and a total amount spent per merchant.
 8. The method ofclaim 1, further comprising: providing a software module via a paymentcard issuer to said merchant before said sending, said module configuredfor receiving said second information based at least in part on saidsending.
 9. A method comprising: maintaining, via a payment card issuercomputer system, first payment card information for a cardholder, saidfirst information associated with a transaction history; processing, viasaid system, a first card not present transaction between saidcardholder and a merchant, said first transaction based at least in parton said first information, said history listing said first transaction;generating, via said system, second payment card information for saidcardholder, said second information replacing said first information forsubsequent use via said cardholder; selecting, via said system, saidmerchant from said history based at least in part on said firsttransaction, said selecting based at least in part on said secondinformation replacing said first information; sending, via said system,said second information to said merchant based at least in part on saidselecting; processing, via said system, a second card not presenttransaction between said cardholder and said merchant, said secondtransaction based at least in part on said second information after saidsending.
 10. The method of claim 9, further comprising: requesting, viasaid system, an authorization from said cardholder for said sending. 11.The method of claim 9, further comprising: receiving, via said system, amessage from said merchant, said message confirming a receipt of saidsecond information based at least in part on said sending.
 12. Themethod of claim 9, further comprising: receiving, via said system, amessage from said merchant, said message confirming a storage of saidsecond information on a storage medium associated with said merchant.13. The method of claim 9, wherein said selecting is based at least inpart on a computerized analysis of said history, said analysis is basedat least in part on at least one of a frequency of use, an amount pertransaction, and a total amount spent per merchant.
 14. The method ofclaim 9, further comprising: providing a software module via a paymentcard issuer to said merchant before said sending, said module configuredfor receiving said second information based at least in part on saidsending.
 15. The method of claim 9, further comprising: receiving, viasaid system, an input from said cardholder, said input modifying aselection of said merchant based at least in part on said selecting. 16.The method of claim 9, further comprising: receiving, via said system,an input from said cardholder, said input confirming said selecting. 17.The method of claim 9, further comprising: providing, via said system, alist to said cardholder, said list including a plurality of merchants,said merchants including said merchant, said list generated based atleast in part on said selecting; receiving, via said system, an inputfrom said cardholder, said input electing said merchant on said list forsaid sending.
 18. The method of claim 9, further comprising: receiving,via said system, an input from said cardholder, said input providing anidentification of said merchant.